Nectar Logo

User-Centred Requirements Handbook

Telematics Engineering Logo

Phase 3. User requirements documentation


3.6 User interface design

Objective

This section specifies details of the user interface that the system will offer to support each user group. This may include:

• an outline of the user interface structure, based on the system concepts

• example screens.

It should also record further details of the software that will be used to create each user-system interface (e.g. development package to be used, standards containing screen layout templates, etc.).

Process

1. Review all the potential user requirements identified in Stages 1 and 2, particularly in Form 1.6 Technical characteristics and 2.2 Design constraints. Copy those that relate to the software interface into Form 3.6 below.

2. Remove any requirements that duplicate others or do not seem relevant.

3. Add any new requirements which arise from the review of this section.

Please refer to RESPECT D4.2, section 2.2 which describes formal characteristics of user interface specifications. Section 2.3 describes a set of principles for user interface specifications based on the concepts of task adequacy, self-descriptiveness, controllability, conformity to user expectations, error tolerance, flexibility and learnability. Section 2.4 presents an outline for documenting the user interface.

Form 3.6 - User interface design (Example 1)

3.6 User Interface Design

Interface name: 1. Customer interface to bank machine
Transfer from Form 1.4 Technical environment
Transfer from Form 1.10 Design ideas and concepts
Pri. Ach. Ref.

Purpose
This is the interface by which members of the public will obtain services from the bank machine.
     

Features
Cash limit display.
Indication of date of balance

3
9

**
**
1.8.6

Components of interface
Main screen structure shown in document: 'Kiosk style guide v2'.
Con -  

Standards to be used
ISO DIS 9241-14 Menu dialogues
4 *  

Example screens
Screen templates shown in document: 'Proposed user Interface Style guide', section 1
Con -  

Tools to be used for building interface
Borland C++ and Screen Builder
Con -  

Form 3.6 - User interface design (Example 2)


Transfer from Form 1.4 Technical environment
Transfer from Form 1.10 Design ideas and concepts
3.6 User Interface Design

Interface name:
2. Bank staff interface to bank machine
Pri. Ach. Ref.

Purpose
This is the interface by which bank staff will maintain the machine and refill it with materials.
     

Methods of interaction
Full keyboard, function keys and monochrome screen.
Con - 1.8.6

Components of interface
Main screen structure shown in document: 'Proposed user Interface Styleguide', section 2
Con -  

Standards to be used
ISO DIS 9241-14 Menu dialogues.
4 *  

Example screens
Screen templates shown in document: 'Kiosk style guide v2''.
Con -  

Tools to be used for building interface Borland C++ and Screen Builder. Con —


3.7 User Support
Back to Contents

NECTAR Home Page The NECTAR Information Update The NECTAR Repository The European Journal of Engineering for Information Society Applications The NECTAR Discussion Fora